Figure 1: Example of Call Park Retrieve in a Cluster
If you have programmed a unique Feature DN at each element, the following feature access codes function normally with remote directory numbers:
Call Forwarding - Follow Me (Always)
Call Forwarding - Busy (Internal and External Source)
Call Forwarding - No Answer (Internal and External Source)
Call Forwarding - I'm Here (both extensions must have remote directory numbers in the cluster network)
Call Forwarding - Follow Me - Third Party (both extension must have remote directory numbers in the cluster network)
Call Forwarding - Override
Call Forwarding - Follow Me - End Chaining
Call Forwarding - Follow Me - Reroute When Busy
Remote Do Not Disturb - Setup and Cancel
Trunk Answer From Any Station (TAFAS)
Call Hold - Remote Retrieve
Call Pickup - Directed
Hotel Room Monitor - Listen
Clear All Features - Remote
Message Waiting - Activate, Deactivate, and Inquiry (only if invoked by a voice mail hunt group member)
Group/Direct Page
DSS/BLF keys
NOTES
Programming for Call Forwarding - COS Option Call Forwarding (Internal Destination) must be enabled in the class of service of the forwarding set.
Call Forwarding Conditions - COS Option Call Forwarding - Accept does not prevent a remote directory number device from receiving a forwarded call (i.e., you can forward your calls to a remote directory number station even if COS Option Call Forward - Accept at that station is set to "No").
From an attendant console, you cannot set up or cancel call forwarding on a remote directory number station.
Remote Portable Directory Numbers (PDNs) are also referred to as Remote Directory Numbers (RDNs).
To make the following features operate within a cluster network, you must use special ARS programming:
Attendant Hold - Remote Retrieve
Dialed Night Service
Individual Trunk Access
Paging (Loudspeaker)
For example, to program the Attendant Hold - Remote Retrieve in a cluster network for an attendant console you would:
Program a Call Park Remote Retrieve feature access code on the node with the attendant console (Node B).
Do not program a Call Park Remote Retrieve feature access code on the other nodes, that is, leave the access code blank.
On the other nodes (Node A), program ARS routes with leading digits that match the Call Park Remote Retrieve feature access code plus three digits to follow.
When the user dials the Call Park Remote Retrieve feature access code, followed by the call park number, the call is routed to the attendant through ARS. The leading ARS digits and the call park number are sent to the attendant node. On the attendant node these digits translate to the Call Park Remote Retrieve feature access code plus the call park number. The feature is then activated and the call is retrieved from the attendant console (see Figure 1: Example of Call Park Retrieve in a Cluster).
|
Figure 1: Example of Call Park Retrieve in a Cluster |